reservations-eapi icon

reservations-eapi

(0 reviews)

Error handling


Whilst every effort will be made to capture all errors which may be returned for these API resources on this page, consumers are advised that as RDG are using a common service (frequently known as Software as a Service or SaaS) for the underlying technology within the reservation service, additional error cases may be added to the product at any time. If you are returned an error not recorded here, please provide details to RDG, including the request which generated the error and the error message itself, and we will investigate and add to this page.


If a request passes the policy checks it will be submitted to the relevant RDG API which may then result in an RDG specific error as opposed to a generic platform error. APIs on the RDG Developer Portal use the following common error format to contain and return these errors to consumers (See RDG Error Object data type):

{
    "errors": [
        {
            "code": "error_code",
            "message": "error message",
            "timestamp": "YYYY-MM-DDTHH:MM:SS",
            "context": {
                "{key}": "value"
            }
        }
    ]
}

The (optional) context object is an unspecified list of key value pairs, allowing contextual information to be provided without requiring a schema definition.

Reservations specific error handling

For the reservations service, the below list represents the known context keys which may be returned by the source service. This list is not within RDG control and is subject to change at any time. Please report any context keys which are not in the list below to cci-support@raildeliverygroup.com and RDG will review and update this page to include them.

Field name keys:
- location
- disabilityType
- rsid
- departureDate
- serviceOriginDate
- ticketTypeCode
- routeCode
- statusCode

There may also be context items which are not field names, such as:
- expected
- got
- reason
- description

Known Error Cases
General
CodeMessageComment
GBR-AUTH-2000Security ErrorWhen RDG fails to process request due to client side or server side security failure
GBR-AUTH-2001Unauthorised UserWhen user’s token is invalid
GBR-AUTH-2002Security validation: precondition failed-
GBR-AUTH-2003Security validation: Bad requestWhen request payload has failed to process
GBR_EXCEPTION_0000Unknown ErrorCatch all for any unknown errors
GBR_EXCEPTION_0001Undefined error by 3rd party systemUnknown error from 3rd party APIs
GBR_EXCEPTION_3000Invalid schema/ Invalid payloadBad request due to payload not conforming to the json/xml schema definition
GBR_EXCEPTION_3001Internal ErrorUnable to complete operation
GBR_EXCEPTION_3006Resource not foundWhen API resource request is not found or not defined in the specification
GBR_EXCEPTION_3007Method not allowedWhen API resource request doesn’t conform to the API specfication e.g. method GET is expected for a resource but POST or PUT call is made
GBR_EXCEPTION_3009Unsupported media typeWhen API resource request media type (e.g. application/json) doesn’t conform to the expected media type
GBR_EXCEPTION_3010HTTP too many requestsRate-limit exceeded
GBR_EXCEPTION_3011AWS S3 bad request errorWhen AWS S3 throws error due to processing error of the request
GBR_EXCEPTION_3012Invalid schema/ Invalid payloadBad request due to payload not conforming to the json/xml schema definition
GBR_EXCEPTION_3013Invalid schema/ Invalid payloadBad request due to payload not conforming to the json/xml schema definition
GBR_EXCEPTION_3014Forbidden ErrorWhen source system doesn’t allow access to a particular resource for a specfic client
GBR_EXCEPTION_3015Validation Error [Email is valid]The structural conformation of email is checked and throws error if doesn’t match the built in REGEX pattern
GBR_EXCEPTION_3063Expression errorWhen any form of REGEX failed to excute due to incorrect inputs
GBR_EXCEPTION_3065Retry exhausted, Redelivery ExhaustedRetry component reaches the threshold number with respect to HTTP requests made
GBR_EXCEPTION_3066Connectivity issue or service is not availableWhen cannot reach the resource URL or underneath service doesn’t respond
GBR_EXCEPTION_3067HTTP time outWhen the HTTP request gets timed out
RAML_ERRORInvalid schema/ Invalid payloadBad request due to payload not conforming to the json/xml schema definition
Availability
CodeMessageComment
could_not_find_disability_typen/aA requested disability type is invalid
could_not_find_passenger_typen/aA requested status code is invalid
could_not_find_productn/aA requested product is invalid
could_not_find_stationn/aA requested station could not be found or is invalid
could_not_find_tariff_groupn/aA requested route code is invalid
invalid_fieldn/aAn invalid value has been specified within a restricted field
over_max_booking_sizen/aNumber of passengers greater than permitted
sales_restrictionn/aReservations cannot be made on a requested service
service_not_in_rostern/aA requested service could not be found
value_not_uniquen/aReturned if the same identifier is used more than once

Last update: 05-Aug-2024 14.00: ASSIST API Documentation Maintenance: 'reservations-eapi', Version 'v2', Page 'Error handling', Revision 'B'.

To request updates to this text please contact Neil Barkham.


Reviews